docs.rs failed to build libp2prs-swarm-0.2.2
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
libp2prs-swarm-0.2.0
High level manager of the network.
A [Swarm] contains the state of the network as a whole. The entire
behaviour of a libp2p network can be controlled through the Swarm.
The Swarm struct contains all established connections to remotes and
manages the state of all the substreams that have been opened, and all
the upgrades that were built upon these substreams.
Initializing a Swarm
Creating a Swarm requires three things:
- A network identity of the local node in form of a [
PeerId]. - One or more implementations of the [
Transport] trait. This is the type that will be used in order to reach nodes on the network based on their address. See thetransportmodule for more information. - One or more implementations of the [
ProtocolHandler] trait. This is the protocols thatSwarmis going to support.
Protocol Handler
The [ProtocolHandler] trait defines how each active connection to a
remote should behave: how to handle incoming substreams, which protocols
are supported, etc.